Reactivate tests in org.eclipse.core.tests.resources #525 #605
Conversation
Michael5601
changed the title
Michael5601
force-pushed
the
PlatformResourcesPerformanceTests
branch
from
f93e02c
to
752e937
Compare
…#525 In this commit, the performance test from the Marker Test class is reactivated because it can be run quickly and successfully. Contributes to eclipse-platform#525
Michael5601
force-pushed
the
PlatformResourcesPerformanceTests
branch
from
752e937
to
a39bf90
Compare
Test Results 42 files + 2 42 suites +2 1h 5m 8s ⏱️ + 11m 4s For more details on these failures, see this check. Results for commit 9c4fca6. ± Comparison against base commit adca2ac. ♻️ This comment has been updated with latest results. |
|
The failing test is random failing test #488. |
…#525 In this commit, the performance test from the Marker Test class is reactivated because it can be run quickly and successfully. Contributes to eclipse-platform#525
mickaelistria
force-pushed
the
PlatformResourcesPerformanceTests
branch
from
a39bf90
to
9c4fca6
Compare
|
The enabled method is no actual test method but only some code measuring and printing the time required for processing operations on markers. I gues it was used around 20 years ago when implementing the functionality to get some insights into the implementation's performance. I don't see that it still has any use but may only produce maintenance effort. I would propose to change this PR (or replace it by a new one) so that the two |
…m/CodeLtDave/eclipse.platform into PlatformResourcesPerformanceTests
In this commit, the deactivated performance tests "_testPerformanceManyResources()" and "_testPerformanceOneResource()" from MarkerTest.java in org.eclipse.core.tests.resources are deleted because they are not real test methods but rather used for code measuring and printing the time for processing operations on markers. See also eclipse-platform#605 (comment). Contributes to eclipse-platform#525
I have added a new PR with the requested changes. (See #674) |
In this commit, the deactivated performance tests "_testPerformanceManyResources()" and "_testPerformanceOneResource()" from MarkerTest.java in org.eclipse.core.tests.resources are deleted because they are not real test methods but rather used for code measuring and printing the time for processing operations on markers. See also eclipse-platform#605 (comment). Contributes to eclipse-platform#525
In this commit, the deactivated performance tests "_testPerformanceManyResources()" and "_testPerformanceOneResource()" from MarkerTest.java in org.eclipse.core.tests.resources are deleted because they are not real test methods but rather used for code measuring and printing the time for processing operations on markers. See also #605 (comment). Contributes to #525
In this commit, the deactivated performance tests "_testPerformanceManyResources()" and "_testPerformanceOneResource()" from MarkerTest.java in org.eclipse.core.tests.resources are deleted because they are not real test methods but rather used for code measuring and printing the time for processing operations on markers. See also eclipse-platform#605 (comment). Contributes to eclipse-platform#525
In this commit, the deactivated performance tests "_testPerformanceManyResources()" and "_testPerformanceOneResource()" from MarkerTest.java in org.eclipse.core.tests.resources are deleted because they are not real test methods but rather used for code measuring and printing the time for processing operations on markers. See also eclipse-platform#605 (comment). Contributes to eclipse-platform#525
In this commit, the performance test from the Marker Test class in org.eclipse.core.tests.resources is reactivated because it can be run quickly and successfully. Contributes to #525